Mayank Jain, product designer.
I make complex digital products feel obvious.
{{ p.summary }}
{{ p.role }}
“He consistently makes projects better, no matter the context or domain.”
“Mayank’s ability to blend technical skill with a deep understanding of client needs sets him apart as a true asset in the UX design field.”
“What stood out was his ability to combine strong user research with thoughtful design execution.”
Hi, I'm Mayank.
Product designer with 10+ years across B2B, SaaS and enterprise products. Most recently in logistics and fulfillment at ShipBob.
I design digital products end to end, from discovery to launch, with my deepest work in operational software: order management, warehouse tools, rate cards and tracking pages.
In animation, visual effects and graphic design. That grounding in craft is what I now bring to simplifying complex flows.
{{ x.desc }}
People using operational tools are busy and mid-task. The screen should make the next action obvious, even with a thousand orders on it.
The happy path is the easy part. Errors, edge cases and empty states are where products earn trust, so I map them before I draw anything.
A good pattern solves a problem once for every team. I design components and rules that keep products consistent as they grow.
Design isn’t finished at launch. I set a baseline, track adoption and support load, and bring the numbers back into the next iteration.
Case studies.
Deep dives into recent B2B work: the problem, my role, and what changed after launch.
{{ p.summary }}
{{ p.role }}
{{ p.summary }}
{{ p.role }}
Order management revamp
Rebuilding the order dashboard merchants use every day to run fulfilment, from ingestion through completion.
The order dashboard was designed for simple D2C orders: one order, one shipment. As B2B order types, split shipments and new exception statuses were added on top, merchants could no longer tell what needed their attention. The legacy platform underneath made every fix slow and risky to ship.
Led design from knowledge transfer to beta: research with merchants and internal teams, a two-level status model, a shipment drawer and new filters, validated in two rounds of testing.
Common jobs 50–72% faster after GA. Fifteen exception reasons now roll up into one status, and the page runs on the new micro-frontend.
ShipBob’s order dashboard was built for a simple D2C flow: one order in, one shipment out. Over time B2B arrived — EDI, dropship, API, manual and FBA orders — and was fitted into the same screens.
Orders started splitting across fulfilment centres, and exception handling grew into a pile of one-off statuses. Merchants use this screen every day to answer urgent questions, and it had stopped answering them quickly. I led design across discovery, ideation, validation, build support and beta launch.
The page ran on the legacy PhotoPrint / Merch App stack, so new features were slow and risky to build. Feature requests were piling up with no clear path to implementation.
“The current filter view scrolls forever — you just scroll and then you can’t remember what you already saw.”
Merchant, during stakeholder interview
- Fulfilment cost
- Business growth
- Shipping revenue
- Shipment and order velocity
- Which SKUs sold today, against marketing promos
- Hit a high SLA rate
- Control cost, by sales channel
- Get fulfilment statuses and item quantities for the day
- Check exception and on-hold orders, resolve, get them shipped
- Create B2B orders from a PO and shipping plan
- Check shipping status to answer “where is my order”
- Create a replacement order
- Update and edit order information
Measured after GA — live merchant data, not a usability lab. Time to complete common jobs, old page vs new, on the same scale.
“I absolutely love the latest update and the new orders page view! It’s a fantastic improvement.”
On seeing the new list page“I like what you have done with the side panel. I don’t need to go to another tab. The filters are easier to use now.”
On the new shipment drawer and filters“I don’t need to go to a new page to see this? Tears are coming to my eyes.”
On seeing the new shipment drawer“I love that page, it’s great. It’s much easier to drill down into stuff.”
On seeing the new list page“Delivered date is a huge improvement. It couldn’t have come at a better time.”
On seeing the new filter panel“This was super clutch, it was really helpful.”
On filtering ~8,000 orders affected by a carrier outageThe order page moved off the legacy PhotoPrint stack onto ShipBob’s new MFE architecture. The backlog of order-management feature requests now has a path to implementation.
Side projects and experiments.
Things I build outside client work to try new tools, ideas and ways of designing.
Flow ScoperTeams scope the one flow they picture, the happy path. Errors show up as bugs after launch, and alternate routes (a support agent doing it by hand, someone finishing on a phone) already exist in real use but nobody designed them. AI means PMs, founders and engineers now ship features without a designer in the room, and they miss the habit of asking "what else could happen here?"
An AI skill that works in Claude, ChatGPT, Gemini or any AI chat. It asks eight short context questions, lays out the happy path, finds the alternate routes, and walks a 17-category checklist for what can go wrong, tied to your answers instead of generic errors. It outputs a plain-language breakdown, open design questions and a branching flow diagram.
Not everyone can install a skill, so I built a copy-prompt page: fill in a short form, copy the prompt, paste it into the AI tool you already use. No install, no sign-up. I tuned it for phones too, with a fixed Copy bar that hides while you type.
- Plain language over jargon, so a designer, an engineer and a stakeholder read the same page.
- Every question is skippable, and the output says which branches stayed generic because of it.
- Alternate paths are separate from failures, because "another valid way in" and "something broke" need different responses.
A full example session for an "Invite teammate" flow.
Help me scope an "Invite teammate" flow for our B2B SaaS web app. An Admin opens Team settings, enters an email and picks a role (Admin or Member), and the teammate gets an email with a link to join.
Users: workspace Admins (inviting) and invited teammates (new to the product). Web only, US only for now. We use a third-party email service to send invites. Business rules: seats are limited by plan, and invite links expire after 7 days. Known pain point: people say they never got the email.
- {{ h }}
- {{ q }}
